The last part of the PRA is to check whether the result of session(s) or interviews is sufficiently complete. Test goals, characteristics (think of the non-functional quality characteristics!) and/or object parts can be used to this end. If a characteristic has not been addressed, is it because it is associated with very little risk or because it has been forgotten? Requirements can also be used here, but attention must be paid that the number remains controllable. User requirements are easily controllable. Business requirements are too abstract for testing (“modifi cation in system must generate 10% more turnover”) and there are probably too many system requirements.

When inventorying risks per quality characteristic, you can use the overview of quality characteristics and the “Checklist of risk factors per quality characteristic”. This checklist can be found on www.tmap.net.

The completeness check can be done in two ways:

1. As part of the session
2. If there is no time: in a separate session with the 2 or 3 main stakeholders, prepared by the test manager.

The complete PRA result is circulated to the participants and client for approval and with the question if there are any additional comments. The test manager incorporates these, unless he expects that they will lead to too much discussion. The client gives definitive approval and makes a decision in the event of any points of discussion.